User defined wire appearance indicating communication functionality in a graphical programming environment

ABSTRACT

System and method for configuring a wire appearance in a graphical programming environment. A first data type (or class), or communication functionality between nodes, e.g., timing, or data transfer, e.g., data transfer semantics, mechanism, or medium, in a graphical program is specified in response to user input. A first wire appearance denoting the first data type or specified functionality is created in response to user input, including, e.g., a specified wire pattern, thickness, shape, color(s), portion of the wire to be configured with the first wire appearance, wire label and/or wire icon to be displayed on or near the wire. A graphical program including a first icon and a second icon is created, including connecting the first icon to the second icon in response to user input, and displaying a wire between the first icon and the second icon in response, where the wire has the first wire appearance.

FIELD OF THE INVENTION

The present invention relates to the field of graphical programming, andmore particularly to a system and method for configuring a wireappearance in a graphical programming environment.

DESCRIPTION OF THE RELATED ART

Graphical programming has become a powerful tool available toprogrammers. Graphical programming environments such as the NationalInstruments LabVIEW product have become very popular. Tools such asLabVIEW have greatly increased the productivity of programmers, andincreasing numbers of programmers are using graphical programmingenvironments to develop their software applications. In particular,graphical programming tools are being used for test and measurement,data acquisition, process control, man machine interface (MMI),supervisory control and data acquisition (SCADA) applications, modeling,simulation, image processing/machine vision applications, and motioncontrol, among others.

A user may assemble a graphical program by selecting various icons ornodes which represent desired functionality, and then connecting thenodes together to create the program. The nodes or icons may beconnected by lines representing data flow between the nodes, controlflow, or execution flow. Thus the block diagram may include a pluralityof interconnected icons such that the diagram created graphicallydisplays a procedure or method for accomplishing a certain result, suchas manipulating one or more input variables and/or producing one or moreoutput variables. In response to the user constructing a diagram orgraphical program using the block diagram editor, data structures and/orprogram instructions may be automatically constructed which characterizean execution procedure that corresponds to the displayed procedure. Thegraphical program may be compiled or interpreted by a computer.

In the course of developing graphical programs, users may desire todefine first data types or to specify communication functionality, e.g.,data transfer functionality or timing, e.g., between nodes in thegraphical program. In some graphical programming systems, a wireconnecting an output of one node to another node in the graphicalprogram may be considered to have or be associated with the data type ofthe node output. However, in prior art graphical programming systems,such wires either all have the same appearance, or have some defaultappearance, and there is no way for a user to specify the appearance ofwires associated or used with user-defined data types or classes.Similarly, there are no current means a user to specify a wireappearance to indicate a specified communication functionality.

Thus, improved systems and methods for specifying graphical programsdesired.

SUMMARY OF THE INVENTION

Various embodiments of a system and method for configuring a wireappearance in a graphical programming environment are presented. Thewire appearance may be at least partially (or completely) unique orspecific to a certain wire type, e.g., wire data type, or a specifiedcommunication functionality. Thus the appearance of this wire in agraphical program provides a visual indication to the user as to thenature of the wire, e.g., the type of data being conveyed on the wireand/or the communication functionality of the wire.

In one embodiment, a first data type may be created in response to userinput. The first data type may be any type desired by the user. Forexample, the first data type may be a type of cluster, a class, or anyother type of data or data structure. The first data type may be createdin any of a variety of ways. For example, the user may invoke a tool tocreate the first data type.

A first wire appearance for the first data type (or class) may becreated in response to user input. In preferred embodiments, creatingthe first wire appearance may include displaying a graphical userinterface (GUI) for configuring the first wire appearance, receivinguser input to the GUI specifying one or more of a wire pattern, a wirethickness, a wire shape, and/or one or more wire colors, and creatingthe first wire appearance in accordance with the user input to the GUI.Note that other appearance attributes may be included as desired,including, for example, a shape, a 3D appearance, a tube appearance, aseparated appearance (e.g., a “dashed” wire), a curved appearance, or an“extrusion shape”, e.g., “rectangular cross-section”, among others. Inother words, any visual aspect of the wire may be used as desired todenote the specified data type (e.g., class) of the wire.

A graphical program may be created, e.g., on the computer system (or ona different computer system), e.g., by the user arranging on a display aplurality of nodes or icons and then interconnecting the nodes to createthe graphical program, automatically, or via any other graphical programcreation methods desired. Creating the graphical program may includeincluding a first icon and/or second icon which is operable to generateand/or receive the first data type and connecting the first icon to thesecond icon in response to user input. In response to the connecting, awire may be displayed between the first icon and the second icon, wherethe wire has the first wire appearance. In other words, the wire thatconnects the first icon or node to the second icon or node may bedisplayed with the wire appearance specified by the user mentionedabove.

While the above embodiments are directed to defining and configuringwire appearance based on a user-defined data type or class, in otherembodiments, the user may define and configure wire appearance based onother attributes, or more generally, based on specified functionalityfor communication between nodes in a graphical program. Thus, forexample, first communication functionality between nodes in a graphicalprogram may be specified in response to user input.

In various embodiments, specifying first communication functionalitybetween nodes may include any of a plurality of communicationfunctionalities, including, for example, timing, and/or data transfer,among others. Thus, for example, the user may provide input specifyingcommunication of timing information between the nodes as opposed to datatransfer (or, alternatively, data transfer between the nodes, as opposedto timing). Specifying timing may include, for example, specifying aclock, e.g., a source for a clock signal, specifying a timing signal, orspecifying whether a leading or trailing edge of the clock or timingsignal is to be used, among others. In other words, specifying timingmay include specifying any attributed of timing functionality, asdesired. Specifying data transfer may include specifying data transfersemantics, a data transfer mechanism, and/or a data transfer medium.Data transfer semantics refers to the manner, e.g., policy, of datatransfer, e.g., synchronous, asynchronous, first-in, first-out (FIFO),buffered, etc., and where data transfer mechanism refers to how thesemantics are implemented, e.g., via direct memory access (DMA), TCP/IP,shared memory, tags, and so forth. Thus, for one example, the user mayspecify that data are to be communicated between two nodesasynchronously, and may also specify that this asynchronous datatransfer be implemented via a particular data structure, e.g., a queueimplemented via a linked list. Specifying a data transfer medium, whichmay also be referred to as a data transport medium, may specify thephysical medium by which the data are transferred, e.g., physical mediasuch as wires, buses, Ethernet, etc., and/or wireless means, amongothers.

A first wire appearance may be created in response to user input, wherethe creating includes storing the first wire appearance. The first wireappearance is useable to be displayed for a wire in a graphical programthat is configured to implement the specified first communicationfunctionality, and visually denotes the specified first communicationfunctionality of the wire. The user may define a wire appearance for acertain wire/wire functionality via a GUI, as described above. Forexample, the user may use a graphical user interface as described aboveto create a wire appearance that is unique or specific to the configuredwire communication functionality.

In one embodiment, specifying communication functionality between nodesmay include specifying functionality of at least one endpoint of thewire. For example, the behavior or mechanism of the “source” or“destination” end of the wire may be specified. Thus, for example, awire that is buffered may be specified to validate any data from thedata source (node) before placing the data on the wire, i.e., thebehavior of the “source” end of the wire may be specified. As anotherexample, the “destination” end of the wire may be specified to outputdefault values if no data are currently on the wire. As an example ofspecifying data transfer mechanisms, the “source” end of the wire may bespecified to communicate with the source node via TCP/IP, while the“destination” end of the wire may be specified to communicate with thedestination node via register access.

In some embodiments, the first wire appearance may be a specifiedappearance of a portion of the wire proximate to the at least oneendpoint of the wire. In other words, some aspects of the wire'sappearance may be specific to the end or ends, and may denotefunctionality thereof. Thus, depending upon the specified functionalityor functionalities of the wire, various portions of the wire may bedisplayed with respective appearances, e.g., patterns, colors,thicknesses, shapes, labels, icons, decorations, etc., as desired, todenote respective communication functionalities of the wire. Thus,creating the first wire appearance for the first communicationfunctionality may include displaying a graphical user interface (GUI)for specifying the first wire appearance, and receiving user input tothe GUI specifying one or more of: a wire pattern, one or more wirecolors, a wire thickness, a wire shape, at least a portion of the wireto be configured with the first wire appearance, a wire label, and/or awire icon to be displayed on or near the wire, and creating the firstwire appearance in accordance with the user input to the GUI.

A first graphical program may be created, where the first graphicalprogram includes a plurality of interconnected icons which visuallyindicate functionality of the first graphical program, including a firsticon and a second icon. Creating the first graphical program may includeconnecting the first icon to the second icon in response to user input,and displaying a wire between the first icon and the second icon inresponse to the connecting, where the wire has the first wire appearancedenoting or indicating the specified first communication functionality.

Thus, various embodiments of the above systems and methods may allow auser to define or specify data type and/or communication functionalityfor communication between two nodes in a graphical program, as well as afirst wire appearance indicating, representing, or denoting thespecified data type or communication functionality. The first wireappearance may then be used in a graphical program to visually indicatewires with that data type or functionality.

BRIEF DESCRIPTION OF THE DRAWINGS

A better understanding of the present invention can be obtained when thefollowing detailed description of the preferred embodiment is consideredin conjunction with the following drawings, in which:

FIG. 1A illustrates a computer system operable to execute a graphicalprogram according to an embodiment of the present invention;

FIG. 1B illustrates a network system comprising two or more computersystems that may implement an embodiment of the present invention;

FIG. 2A illustrates an instrumentation control system according to oneembodiment of the invention;

FIG. 2B illustrates an industrial automation system according to oneembodiment of the invention;

FIG. 3A is a high level block diagram of an exemplary system which mayexecute or utilize graphical programs;

FIG. 3B illustrates an exemplary system which may perform control and/orsimulation functions utilizing graphical programs;

FIG. 4 is an exemplary block diagram of the computer systems of FIGS.1A, 1B, 2A and 2B and 3B;

FIGS. 5A and 5B flowchart embodiments of a method for configuring a wireappearance indicating data type in a graphical programming environment;

FIGS. 6-8 illustrate a GUI for configuring a wire appearance, accordingto one embodiment;

FIG. 9 illustrates an exemplary graphical program utilizing user-defineddata types with corresponding wires, according to one embodiment;

FIGS. 10A and 10B flowchart embodiments of a method for configuring awire appearance indicating communication functionality in a graphicalprogramming environment;

FIG. 11 illustrates an exemplary graphical program utilizing variouscommunication functionalities with corresponding wires, according to oneembodiment.

While the invention is susceptible to various modifications andalternative forms, specific embodiments thereof are shown by way ofexample in the drawings and are herein described in detail. It should beunderstood, however, that the drawings and detailed description theretoare not intended to limit the invention to the particular formdisclosed, but on the contrary, the intention is to cover allmodifications, equivalents and alternatives falling within the spiritand scope of the present invention as defined by the appended claims.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

Incorporation by Reference

The following references are hereby incorporated by reference in theirentirety as though fully and completely set forth herein:

U.S. Pat. No. 4,914,568 titled “Graphical System for Modeling a Processand Associated Method,” issued on Apr. 3, 1990.

U.S. Pat. No. 5,481,741 titled “Method and Apparatus for ProvidingAttribute Nodes in a Graphical Data Flow Environment”.

U.S. Pat. No. 6,173,438 titled “Embedded Graphical Programming System”filed Aug. 18, 1997.

U.S. Pat. No. 6,219,628 titled “System and Method for Configuring anInstrument to Perform Measurement Functions Utilizing Conversion ofGraphical Programs into Hardware Implementations,” filed Aug. 18, 1997.

U.S. Patent Application Publication No. 20010020291 (Ser. No.09/745,023) titled “System and Method for Programmatically Generating aGraphical Program in Response to Program Information,” filed Dec. 20,2000.

U.S. patent application Ser. No. 11/462,393, titled “Asynchronous Wiresfor Graphical Programming”, filed Aug. 4, 2006.

U.S. patent application Ser. No. 11/759,975, titled “Graphical DiagramWhich Automatically Determines a Data Transport Mechanism For WiresBased On Configured Policies”, filed Jun. 8, 2007.

U.S. patent application Ser. No. 11/759,979, titled “Graphical DiagramWires Whose Appearance Represents Configured Semantics”, filed Jun. 8,2007.

U.S. patent application Ser. No. 11/759,985, titled “Configuring Iconsto Represent Data Transfer Functionality”, filed Jun. 8, 2007.

U.S. patent application Ser. No. 11/759,991, titled “Diagram withConfigurable Wires”, filed Jun. 8, 2007.

U.S. patent application Ser. No. 11/743,418, titled “Configurable Wiresin a Statechart”, filed May 2, 2007.

Terms

The following is a glossary of terms used in the present application:

Memory Medium—Any of various types of memory devices or storage devices.The term “memory medium” is intended to include an installation medium,e.g., a CD-ROM, floppy disks 104, or tape device; a computer systemmemory or random access memory such as DRAM, DDR RAM, SRAM, EDO RAM,Rambus RAM, etc.; or a non-volatile memory such as a magnetic media,e.g., a hard drive, or optical storage. The memory medium may compriseother types of memory as well, or combinations thereof. In addition, thememory medium may be located in a first computer in which the programsare executed, or may be located in a second different computer whichconnects to the first computer over a network, such as the Internet. Inthe latter instance, the second computer may provide programinstructions to the first computer for execution. The term “memorymedium” may include two or more memory mediums which may reside indifferent locations, e.g., in different computers that are connectedover a network.

Carrier Medium—a memory medium as described above, as well as a physicaltransmission medium, such as a bus, network, and/or other physicaltransmission medium that conveys signals such as electrical,electromagnetic, or digital signals.

Programmable Hardware Element—includes various hardware devicescomprising multiple programmable function blocks connected via aprogrammable interconnect. Examples include FPGAs (Field ProgrammableGate Arrays), PLDs (Programmable Logic Devices), FPOAs (FieldProgrammable Object Arrays), and CPLDs (Complex PLDs). The programmablefunction blocks may range from fine grained (combinatorial logic or lookup tables) to coarse grained (arithmetic logic units or processorcores). A programmable hardware element may also be referred to as“reconfigurable logic”.

Medium—includes one or more of a memory medium, carrier medium, and/orprogrammable hardware element; encompasses various types of mediums thatcan either store program instructions/data structures or can beconfigured with a hardware configuration program. For example, a mediumthat is “configured to perform a function or implement a softwareobject” may be 1) a memory medium or carrier medium that stores programinstructions, such that the program instructions are executable by aprocessor to perform the function or implement the software object; 2) amedium carrying signals that are involved with performing the functionor implementing the software object; and/or 3) a programmable hardwareelement configured with a hardware configuration program to perform thefunction or implement the software object.

Program—the term “program” is intended to have the full breadth of itsordinary meaning. The term “program” includes 1) a software programwhich may be stored in a memory and is executable by a processor or 2) ahardware configuration program useable for configuring a programmablehardware element.

Software Program—the term “software program” is intended to have thefull breadth of its ordinary meaning, and includes any type of programinstructions, code, script and/or data, or combinations thereof, thatmay be stored in a memory medium and executed by a processor. Exemplarysoftware programs include programs written in text-based programminglanguages, such as C, C++, Pascal, Fortran, Cobol, Java, assemblylanguage, etc.; graphical programs (programs written in graphicalprogramming languages); assembly language programs; programs that havebeen compiled to machine language; scripts; and other types ofexecutable software. A software program may comprise two or moresoftware programs that interoperate in some manner.

Data Type—a classification of a particular type or representation ofinformation. Data types may be intrinsic to a programming language,e.g., integer, character, etc., and/or user-defined, such as, forexample, AccountRecord, ChannelName, and so forth. Data types can beatomic, i.e., specifying a single, simple data object, such as aninteger, or may be compound, such as an array of integers, a characterstring, or a user-defined type that includes multiple data elements ofthe same or different data types. A data type definition specifies thesize of an element of that type, e.g., 16-bits, as well as the structureof the element, e.g., the order and content of a compound data type. Adata type is a type of data, not the data itself, i.e., data elements ofa data type must be instantiated.

Class—a form of compound data type that may specify an ordered list ofcomponent data types, and may also include methods (e.g., memberfunctions) that may access and/or operate on the components. In somesystems, classes may be heritable, i.e., a “child” class may inheritcomponent data types and methods from a “parent” class, and may add dataand/or add to or modify the methods as desired. A class (definition)defines a type of data or object, and is not the object itself, i.e.,objects of a class must be instantiated.

Array—a sequential list structure that includes a variable number ofzero or more data elements. These elements may be all of the same type(a homogenous array) or of differing types (a heterogeneous array). Whenthe elements are of differing types, there is generally some commonparent type from which all the element types are derived, such that thearray can be said to be a homogenous array of that common parent type.For example, a list of dogs may include many types of dogs, such asGerman shepherds, Cocker Spaniels and Dalmatians.

Cluster—a structure that includes a fixed number of multiple dataelements, optionally of different data types.

Aggregate—a collection of data elements, e.g., an array or cluster.

Communication Functionality—the functionality of a communicativeconnection, e.g., a wire, between nodes in a graphical program.Communication functionality may include timing, or data transferfunctionality, such as data transfer semantics, a data transfermechanism, and/or a data transfer medium.

Wire—a graphical representation of data communication between elementsin a graphical program. For example, the plurality of nodes or icons ina graphical program may be interconnected by wires. A wire may have orbe associated with a data type or communication functionality, and mayhave an appearance that indicates the data type of data beingcommunicated over the wire or the communication functionality of thewire.

Hardware Configuration Program—a program, e.g., a netlist or bit file,that can be used to program or configure a programmable hardwareelement.

Graphical Program—A program comprising a plurality of interconnectednodes or icons, where the plurality of interconnected nodes or iconsvisually indicate functionality of the program.

The following provides examples of various aspects of graphicalprograms. The following examples and discussion are not intended tolimit the above definition of graphical program, but rather provideexamples of what the term “graphical program” encompasses:

The nodes in a graphical program may be connected in one or more of adata flow, control flow, and/or execution flow format. The nodes mayalso be connected in a “signal flow” format, which is a subset of dataflow.

Exemplary graphical program development environments which may be usedto create graphical programs include LabVIEW, DasyLab, DiaDem andMatrixx/SystemBuild from National Instruments, Simulink from theMathWorks, VEE from Agilent, WiT from Coreco, Vision Program Managerfrom PPT Vision, SoftWIRE from Measurement Computing, Sanscript fromNorthwoods Software, Khoros from Khoral Research, SnapMaster from HEMData, VisSim from Visual Solutions, ObjectBench by SES (Scientific andEngineering Software), and VisiDAQ from Advantech, among others.

The term “graphical program” includes models or block diagrams createdin graphical modeling environments, where the model or block diagramcomprises interconnected nodes or icons that visually indicate operationof the model or block diagram; exemplary graphical modeling environmentsinclude Simulink, SystemBuild, VisSim, Hypersignal Block Diagram, etc.

A graphical program may be represented in the memory of the computersystem as data structures and/or program instructions. The graphicalprogram, e.g., these data structures and/or program instructions, may becompiled or interpreted to produce machine language that accomplishesthe desired method or process as shown in the graphical program.

Input data to a graphical program may be received from any of varioussources, such as from a device, unit under test, a process beingmeasured or controlled, another computer program, a database, or from afile. Also, a user may input data to a graphical program or virtualinstrument using a graphical user interface, e.g., a front panel.

A graphical program may optionally have a GUI associated with thegraphical program. In this case, the plurality of interconnected nodesare often referred to as the block diagram portion of the graphicalprogram.

Node—In the context of a graphical program, an element that may beincluded in a graphical program. A node may have an associated icon thatrepresents the node in the graphical program, as well as underlying codeor data that implements functionality of the node. Exemplary nodesinclude function nodes, terminal nodes, structure nodes, etc. Nodes maybe connected together in a graphical program by connection icons orwires.

Data Flow Graphical Program (or Data Flow Diagram)—A graphical programor diagram comprising a plurality of interconnected nodes, where theconnections between the nodes indicate that data produced by one node isused by another node.

Graphical User Interface—this term is intended to have the full breadthof its ordinary meaning. The term “Graphical User Interface” is oftenabbreviated to “GUI”. A GUI may comprise only one or more input GUIelements, only one or more output GUI elements, or both input and outputGUI elements.

The following provides examples of various aspects of GUIs. Thefollowing examples and discussion are not intended to limit the ordinarymeaning of GUI, but rather provide examples of what the term “graphicaluser interface” encompasses:

A GUI may comprise a single window having one or more GUI Elements, ormay comprise a plurality of individual GUI Elements (or individualwindows each having one or more GUI Elements), where the individual GUIElements or windows may optionally be tiled together.

A GUI may be associated with a graphical program. In this instance,various mechanisms may be used to connect GUI Elements in the GUI withnodes in the graphical program. For example, when Input Controls andOutput Indicators are created in the GUI, corresponding nodes (e.g.,terminals) may be automatically created in the graphical program orblock diagram. Alternatively, the user can place terminal nodes in theblock diagram which may cause the display of corresponding GUI Elementsfront panel objects in the GUI, either at edit time or later at runtime. As another example, the GUI may comprise GUI Elements embedded inthe block diagram portion of the graphical program.

Front Panel—A Graphical User Interface that includes input controls andoutput indicators, and which enables a user to interactively control ormanipulate the input being provided to a program, and view output of theprogram, while the program is executing.

A front panel is a type of GUI. A front panel may be associated with agraphical program as described above.

In an instrumentation application, the front panel can be analogized tothe front panel of an instrument. In an industrial automationapplication the front panel can be analogized to the MMI (Man MachineInterface) of a device. The user may adjust the controls on the frontpanel to affect the input and view the output on the respectiveindicators.

Graphical User Interface Element—an element of a graphical userinterface, such as for providing input or displaying output. Exemplarygraphical user interface elements comprise input controls and outputindicators

Input Control—a graphical user interface element for providing userinput to a program. Exemplary input controls comprise dials, knobs,sliders, input text boxes, etc.

Output Indicator—a graphical user interface element for displayingoutput from a program. Exemplary output indicators include charts,graphs, gauges, output text boxes, numeric displays, etc. An outputindicator is sometimes referred to as an “output control”.

Computer System—any of various types of computing or processing systems,including a personal computer system (PC), mainframe computer system,workstation, network appliance, Internet appliance, personal digitalassistant (PDA), television system, grid computing system, or otherdevice or combinations of devices. In general, the term “computersystem” can be broadly defined to encompass any device (or combinationof devices) having at least one processor that executes instructionsfrom a memory medium.

Measurement Device—includes instruments, data acquisition devices, smartsensors, and any of various types of devices that are operable toacquire and/or store data. A measurement device may also optionally befurther operable to analyze or process the acquired or stored data.Examples of a measurement device include an instrument, such as atraditional stand-alone “box” instrument, a computer-based instrument(instrument on a card) or external instrument, a data acquisition card,a device external to a computer that operates similarly to a dataacquisition card, a smart sensor, one or more DAQ or measurement cardsor modules in a chassis, an image acquisition device, such as an imageacquisition (or machine vision) card (also called a video capture board)or smart camera, a motion control device, a robot having machine vision,and other similar types of devices. Exemplary “stand-alone” instrumentsinclude oscilloscopes, multimeters, signal analyzers, arbitrary waveformgenerators, spectroscopes, and similar measurement, test, or automationinstruments.

A measurement device may be further operable to perform controlfunctions, e.g., in response to analysis of the acquired or stored data.For example, the measurement device may send a control signal to anexternal system, such as a motion control system or to a sensor, inresponse to particular data. A measurement device may also be operableto perform automation functions, i.e., may receive and analyze data, andissue automation control signals in response.

FIG. 1A—Computer System

FIG. 1A illustrates a computer system 82 operable to various embodimentsof the invention described herein. Various embodiments of a method forconfiguring a wire appearance in a graphical programming environment isdescribed below.

As shown in FIG. 1A, the computer system 82 may include a display deviceoperable to display a graphical program as the graphical program iscreated and/or executed. The display device may also be operable todisplay a graphical user interface or front panel of the graphicalprogram during execution of the graphical program. The graphical userinterface may comprise any type of graphical user interface, e.g.,depending on the computing platform.

The computer system 82 may include a memory medium(s) on which one ormore computer programs or software components according to oneembodiment of the present invention may be stored. For example, thememory medium may store one or more graphical programs which areexecutable to perform the methods described herein. Also, the memorymedium may store a graphical programming development environmentapplication used to create and/or execute such graphical programs. Thememory medium may also store operating system software, as well as othersoftware for operation of the computer system. Various embodimentsfurther include receiving or storing instructions and/or dataimplemented in accordance with the foregoing description upon a carriermedium.

FIG. 1B—Computer Network

FIG. 1B illustrates a system including a first computer system 82 thatis coupled to a second computer system 90. The computer system 82 may beconnected through a network 84 (or a computer bus) to the secondcomputer system 90. The computer systems 82 and 90 may each be any ofvarious types, as desired. The network 84 can also be any of varioustypes, including a LAN (local area network), WAN (wide area network),the Internet, or an Intranet, among others. The computer systems 82 and90 may execute a graphical program in a distributed fashion. Forexample, computer 82 may execute a first portion of the block diagram ofa graphical program and computer system 90 may execute a second portionof the block diagram of the graphical program. As another example,computer 82 may display the graphical user interface of a graphicalprogram and computer system 90 may execute the block diagram of thegraphical program.

In one embodiment, the graphical user interface of the graphical programmay be displayed on a display device of the computer system 82, and theblock diagram may execute on a device 190 connected to the computersystem 82. The device 190 may include a programmable hardware elementand/or may include a processor and memory medium which may execute areal time operating system. In one embodiment, the graphical program maybe downloaded and executed on the device 190. For example, anapplication development environment with which the graphical program isassociated may provide support for downloading a graphical program forexecution on the device in a real time system.

Exemplary Systems

Embodiments of the present invention may be involved with performingtest and/or measurement functions; controlling and/or modelinginstrumentation or industrial automation hardware; modeling andsimulation functions, e.g., modeling or simulating a device or productbeing developed or tested, etc. Exemplary test applications where thegraphical program may be used include hardware-in-the-loop testing andrapid control prototyping, among others.

However, it is noted that the present invention can be used for aplethora of applications and is not limited to the above applications.In other words, applications discussed in the present description areexemplary only, and the present invention may be used in any of varioustypes of systems. Thus, the system and method of the present inventionis operable to be used in any of various types of applications,including the control of other types of devices such as multimediadevices, video devices, audio devices, telephony devices, Internetdevices, etc., as well as general purpose software applications such asword processing, spreadsheets, network control, network monitoring,financial applications, games, etc.

FIG. 2A illustrates an exemplary instrumentation control system 100which may implement embodiments of the invention. The system 100comprises a host computer 82 which connects to one or more instruments.The host computer 82 may comprise a CPU, a display screen, memory, andone or more input devices such as a mouse or keyboard as shown. Thecomputer 82 may operate with the one or more instruments to analyze,measure or control a unit under test (UUT) or process 150.

The one or more instruments may include a GPIB instrument 112 andassociated GPIB interface card 122, a data acquisition board 114 andassociated signal conditioning circuitry 124, a VXI instrument 116, aPXI instrument 118, a video device or camera 132 and associated imageacquisition (or machine vision) card 134, a motion control device 136and associated motion control interface card 138, and/or one or morecomputer based instrument cards 142, among other types of devices. Thecomputer system may couple to and operate with one or more of theseinstruments. The instruments may be coupled to a unit under test (UUT)or process 150, or may be coupled to receive field signals, typicallygenerated by transducers. The system 100 may be used in a dataacquisition and control application, in a test and measurementapplication, an image processing or machine vision application, aprocess control application, a man-machine interface application, asimulation application, or a hardware-in-the-loop validationapplication, among others.

FIG. 2B illustrates an exemplary industrial automation system 160 whichmay implement embodiments of the invention. The industrial automationsystem 160 is similar to the instrumentation or test and measurementsystem 100 shown in FIG. 2A. Elements which are similar or identical toelements in FIG. 2A have the same reference numerals for convenience.The system 160 may comprise a computer 82 which connects to one or moredevices or instruments. The computer 82 may comprise a CPU, a displayscreen, memory, and one or more input devices such as a mouse orkeyboard as shown. The computer 82 may operate with the one or moredevices to a process or device 150 to perform an automation function,such as MMI (Man Machine Interface), SCADA (Supervisory Control and DataAcquisition), portable or distributed data acquisition, process control,advanced analysis, or other control, among others.

The one or more devices may include a data acquisition board 114 andassociated signal conditioning circuitry 124, a PXI instrument 118, avideo device 132 and associated image acquisition card 134, a motioncontrol device 136 and associated motion control interface card 138, afieldbus device 170 and associated fieldbus interface card 172, a PLC(Programmable Logic Controller) 176, a serial instrument 182 andassociated serial interface card 184, or a distributed data acquisitionsystem, such as the Fieldpoint system available from NationalInstruments, among other types of devices.

FIG. 3A is a high level block diagram of an exemplary system which mayexecute or utilize graphical programs. FIG. 3A illustrates a generalhigh-level block diagram of a generic control and/or simulation systemwhich comprises a controller 92 and a plant 94. The controller 92represents a control system/algorithm the user may be trying to develop.The plant 94 represents the system the user may be trying to control.For example, if the user is designing an ECU for a car, the controller92 is the ECU and the plant 94 is the car's engine (and possibly othercomponents such as transmission, brakes, and so on.) As shown, a usermay create a graphical program that specifies or implements thefunctionality of one or both of the controller 92 and the plant 94. Forexample, a control engineer may use a modeling and simulation tool tocreate a model (graphical program) of the plant 94 and/or to create thealgorithm (graphical program) for the controller 92.

FIG. 3B illustrates an exemplary system which may perform control and/orsimulation functions. As shown, the controller 92 may be implemented bya computer system 82 or other device (e.g., including a processor andmemory medium and/or including a programmable hardware element) thatexecutes or implements a graphical program. In a similar manner, theplant 94 may be implemented by a computer system or other device 144(e.g., including a processor and memory medium and/or including aprogrammable hardware element) that executes or implements a graphicalprogram, or may be implemented in or as a real physical system, e.g., acar engine.

In one embodiment of the invention, one or more graphical programs maybe created which are used in performing rapid control prototyping. RapidControl Prototyping (RCP) generally refers to the process by which auser develops a control algorithm and quickly executes that algorithm ona target controller connected to a real system. The user may develop thecontrol algorithm using a graphical program, and the graphical programmay execute on the controller 92, e.g., on a computer system or otherdevice. The computer system 82 may be a platform that supports real timeexecution, e.g., a device including a processor that executes a realtime operating system (RTOS), or a device including a programmablehardware element.

In one embodiment of the invention, one or more graphical programs maybe created which are used in performing Hardware in the Loop (HIL)simulation. Hardware in the Loop (HIL) refers to the execution of theplant model 94 in real time to test operation of a real controller 92.For example, once the controller 92 has been designed, it may beexpensive and complicated to actually test the controller 92 thoroughlyin a real plant, e.g., a real car. Thus, the plant model (implemented bya graphical program) is executed in real time to make the realcontroller 92 “believe” or operate as if it is connected to a realplant, e.g., a real engine.

In the embodiments of FIGS. 2A, 2B, and 3B above, one or more of thevarious devices may couple to each other over a network, such as theInternet. In one embodiment, the user operates to select a target devicefrom a plurality of possible target devices for programming orconfiguration using a graphical program. Thus the user may create agraphical program on a computer and use (execute) the graphical programon that computer or deploy the graphical program to a target device (forremote execution on the target device) that is remotely located from thecomputer and coupled to the computer through a network.

Graphical software programs which perform data acquisition, analysisand/or presentation, e.g., for measurement, instrumentation control,industrial automation, modeling, or simulation, such as in theapplications shown in FIGS. 2A and 2B, may be referred to as virtualinstruments.

FIG. 4—Computer System Block Diagram

FIG. 4 is a block diagram representing one embodiment of the computersystem 82 and/or 90 illustrated in FIGS. 1A and IB, or computer system82 shown in FIGS. 2A or 2B. It is noted that any type of computer systemconfiguration or architecture can be used as desired, and FIG. 4illustrates a representative PC embodiment. It is also noted that thecomputer system may be a general purpose computer system, a computerimplemented on a card installed in a chassis, or other types ofembodiments. Elements of a computer not necessary to understand thepresent description have been omitted for simplicity.

The computer may include at least one central processing unit or CPU(processor) 160 which is coupled to a processor or host bus 162. The CPU160 may be any of various types, including an x86 processor, e.g., aPentium class, a PowerPC processor, a CPU from the SPARC family of RISCprocessors, as well as others. A memory medium, typically comprising RAMand referred to as main memory, 166 is coupled to the host bus 162 bymeans of memory controller 164. The main memory 166 may store one ormore programs, e.g., graphical programs, implementing variousembodiments of the techniques described herein. The main memory may alsostore operating system software, as well as other software for operationof the computer system.

The host bus 162 may be coupled to an expansion or input/output bus 170by means of a bus controller 168 or bus bridge logic. The expansion bus170 may be the PCI (Peripheral Component Interconnect) expansion bus,although other bus types can be used. The expansion bus 170 includesslots for various devices such as described above. The computer 82further comprises a video display subsystem 180 and hard drive 182coupled to the expansion bus 170.

As shown, a device 190 may also be connected to the computer. The device190 may include a processor and memory which may execute a real timeoperating system. The device 190 may also or instead comprise aprogrammable hardware element. The computer system may be operable todeploy a graphical program to the device 190 for execution of thegraphical program on the device 190. The deployed graphical program maytake the form of graphical program instructions or data structures thatdirectly represents the graphical program. Alternatively, the deployedgraphical program may take the form of text code (e.g., C code)generated from the graphical program. As another example, the deployedgraphical program may take the form of compiled code generated fromeither the graphical program or from text code that in turn wasgenerated from the graphical program.

FIGS. 5A and 5B—Method for Configuration of a Wire Appearance for a DataType

FIGS. 5A and 5B illustrate embodiments of a method for configuring awire appearance to indicate data type in a graphical programmingenvironment. The methods shown in FIGS. 5A and 5B may be used inconjunction with any of the computer systems or devices shown in theabove Figures, among other devices. In various embodiments, some of themethod elements shown may be performed concurrently, in a differentorder than shown, or may be omitted. Additional method elements may alsobe performed as desired. As shown, this method may operate as follows.

As FIG. 5A shows, in 502, a first data type may be created in responseto user input. The first data type may be any type desired by the user.For example, the first data type may be a type of cluster, a class, orany other type of data structure. In a preferred embodiment, creatingthe first data type in response to user input may include creating afirst class, where the first class defines the first data type. In anexemplary embodiment, the first data type or class may be an errorcluster, where the error cluster may include various data types forcommunicating and/or characterizing errors, e.g., a Boolean, a numeric,and a string.

The first data type may be created in any of a variety of ways. Forexample, the user may invoke a tool to create the first data type. In anembodiment where the first data type is a first class, creating thefirst class may include invoking a class creation tool, where the classcreation tool includes a graphical user interface (GUI) for receivinguser input specifying the first class. In a preferred embodiment, theclass creation tool may include a wizard that is operable to guide theuser through creating and specifying the first class. As is well knownin the art of programming, a class may include data elements and/orfunctions or methods for accessing and/or operating on the dataelements. Thus, creating the first class may include receiving userinput specifying one or more data elements of the first class, and/orone or more functions of the first class. The one or more functions mayinclude one or more graphical programs, where, as defined above, agraphical program comprises a plurality of interconnected nodes or iconswhich visually indicates the functionality of the program.

In 504, a first wire appearance for the first data type may be createdin response to user input, where the creating includes storing the firstwire appearance. The first wire appearance is useable to be displayedfor a wire in a graphical program that conveys data of the first datatype, and visually specifies that the wire conveys data of the firstdata type. In preferred embodiments, creating the first wire appearancefor the data type in response to user input may include displaying agraphical user interface (GUI) for configuring the first wireappearance, receiving user input to the GUI specifying a wire pattern, awire thickness, a wire shape, and/or one or more wire colors, andcreating the first wire appearance in accordance with the user input tothe GUI. One embodiment of a GUI for configuring the first wireappearance is described below with reference to FIGS. 6-8. In someembodiments, the GUI for configuring the first wire appearance may beincluded in or invoked by the class creation tool (or equivalent)described above in 502. Similarly, in some embodiments, the GUI forconfiguring the first wire appearance and/or the class creation tool maybe included in or invoked by or under the graphical program developmentenvironment.

Note that other appearance attributes may be included as desired,including, for example, a shape, a 3D appearance, a tube appearance, aseparated appearance, a curved appearance, or an “extrusion shape”,e.g., “rectangular cross-section”, among others. In other words, anyvisual aspect of the wire may be used as desired to denote the specifieddata type (e.g., class) of the wire.

In 506, a graphical program may be created, i.e., a first graphicalprogram, e.g., on the computer system 82 (or on a different computersystem). The graphical program may be created or assembled by the userarranging on a display a plurality of nodes or icons and theninterconnecting the nodes to create the graphical program. In responseto the user assembling the graphical program, data structures may becreated and stored which represent the graphical program. The nodes maybe interconnected in one or more of a data flow, control flow, orexecution flow format. The graphical program may thus comprise aplurality of interconnected nodes or icons that visually indicates thefunctionality of the program, as noted above. As also noted above, thegraphical program may comprise a block diagram and may also include auser interface portion or front panel portion. Where the graphicalprogram includes a user interface portion, the user may optionallyassemble the user interface on the display. As one example, the user mayuse the LabVIEW graphical programming development environment to createthe graphical program.

In an alternate embodiment, the graphical program may be created in 506by the user creating or specifying a prototype, followed by automatic orprogrammatic creation of the graphical program from the prototype. Thisfunctionality is described in U.S. patent application Ser. No.09/587,682 titled “System and Method for Automatically Generating aGraphical Program to Perform an Image Processing Algorithm”, which ishereby incorporated by reference in its entirety as though fully andcompletely set forth herein. The graphical program may be created inother manners, either by the user or programmatically, as desired. Thegraphical program may implement a measurement function that is desiredto be performed by the instrument, although, as noted above, in variousembodiments, the graphical program may implement any type offunctionality desired. For example, the graphical program may beoperable to perform one or more of: an industrial automation function, aprocess control function, and/or a test and measurement function, amongothers.

In a preferred embodiment, creating the graphical program may compriseincluding a first icon which corresponds to the first data type and asecond icon in the graphical program and connecting the first icon tothe second icon in response to user input, as indicated in 508. Inresponse to the connecting, a wire may be displayed between the firsticon and the second icon, where the wire has the first wire appearance,as indicated in 510. In other words, the wire that connects the firsticon or node to the second icon or node may be displayed with the wireappearance specified by the user in 504 above.

In one embodiment, creating the graphical program may further includeconnecting an output of the first icon to a third icon, and displaying awire between the first icon and the third icon in response to theconnecting, where the wire has the first wire appearance. In otherwords, where the output(s) of the first node is of the first(user-defined) data type, the wire(s) connecting the output(s) toanother node(s) may be of or associated with the same data type, and maythus be displayed with the user-specified wire appearance.

Thus, the method may include displaying the first wire appearance for afirst wire in a first graphical program, where the first wire conveysdata of the first data type, and where the first wire appearancevisually specifies that the first wire conveys data of the first datatype.

In preferred embodiments, the graphical program may be or include agraphical data flow program, although other types of graphical programare also contemplated, such as, for example, control flow, executionflow, or even state diagrams, among others.

As indicated in 512 and 514 of FIG. 5A, in some embodiments, the methodmay optionally also include modifying the first wire appearance for thedata type in response to user input, and displaying the wire between thefirst icon and the second icon in response, where the wire has themodified first wire appearance. Thus, after the data type and wireappearance have been created and used in the graphical program, the usermay be able to reconfigure or modify the wire appearance, in which casethe wire in the graphical program may be automatically updated inaccordance with the modified wire appearance specified by the user. Thewire appearance may be modified via the same GUI used to create andspecify the wire appearance initially, i.e., as described in 504 above.

In preferred embodiments, the first wire appearance of the data type maybe inheritable, e.g., as is common in object-oriented systems, and sothe first data type may be a user-defined class. As is well known in theart of object-oriented programming, in some systems classes may be usedto derive additional classes via inheritance, where a derived class,referred to as a child class, may inherit all of the data types (e.g.,member elements), and functions or methods of the original class,referred to as a parent class, and may optionally also includeadditional data elements and/or methods or functions. Thus, the methodof FIG. 5B refers to embodiments where the first data types describedabove with reference to FIG. 5A are classes (e.g., first classes), andso in the descriptions below, the user-defined data types are referredto as classes.

As indicated in 522 of FIG. 5B, in some embodiments, the method may alsoinclude creating a second class (data type) in response to user input,where the second class is derived from the first class, i.e., the firstdata type of FIG. 5A. A third icon which corresponds to the second classand a fourth icon may then be included in a second graphical program,e.g., by connecting the third icon to the fourth icon in response touser input, as indicated in 524. A second wire may then be displayedbetween the third icon and the fourth icon in response to theconnecting, where the second wire has the first wire appearance. Inother words, the first wire appearance associated with the firstclass/data type may be inheritable, such that a second class/data typederived from the first class/data type may also inherit the wireappearance of the first class/data type.

The user may also be allowed to modify this inherited wire appearance.For example, the method may also include modifying the first wireappearance for the second class in response to user input, anddisplaying the wire between the third icon and the fourth icon inresponse to the modifying, where the wire has the modified first wireappearance. Thus, the first wire appearance (associated with the firstclass) may serve as a default wire appearance for any derived classesbased on that first class.

Note that in some embodiments, the modification of the inherited wireappearance may be performed as part of the child class specification,where, for example, the wire appearance for the derived class may bespecified prior to inclusion of the connected third and fourth icons inthe (second) graphical program, and so the wire connecting the third andfourth icons may be displayed initially with the derived and modifiedwire appearance. Said another way, the method may include creating asecond class/data type in response to user input, where the secondclass/data type is derived from the first class/data type, and creatinga second wire appearance for the second class/data type in response touser input. A third icon which corresponds to the second class/data typeand a fourth icon may be included in a second graphical program,including connecting the third icon to the fourth icon in response touser input. A second wire may then be displayed between the third iconand the fourth icon in response to the connecting, where the second wirehas the second wire appearance.

It should be noted that the second graphical program mentioned above maybe a different graphical program than the graphical program of 506, ormay be or include the first graphical program. In other words, thederived class/data type and its wire appearance may be used in theoriginal graphical program, or in a different graphical program, asdesired.

Further Data Type Representations

As described above, a user-defined data type or class may be indicatedor represented by the appearance of a wire configured to transmit orcommunicate that data type. Note that the term “data type” refersbroadly to any type of data, data structure, or class, while the term“class” refers specifically to data types that are heritable (i.e.,inheritable), e.g., as used in object-oriented systems andmethodologies. In some embodiments, either in addition to, or insteadof, such user-defined wire appearances, user-defined data types may alsobe represented in other ways. For example, in one embodiment, the datatype may include an icon representing the data type. The icon may bedisplayed in the graphical program to represent a use or instantiationof that data type.

In one embodiment, the graphical program may include a block diagramportion comprising the plurality of interconnected icons, and a userinterface portion, e.g., a front panel. Creating the graphical programmay include adding or including a data element of the first data type inthe graphical program, and displaying the icon of the data type in thegraphical program.

As one example, a data element of the first data type may be included asa constant in the graphical program, and the icon displayed in the blockdiagram portion of the graphical program. As another example, includingthe data element of the first data type in the graphical program maycomprise including the data element as a control or indicator in thegraphical program, where displaying the icon of the data type in thegraphical program may include displaying the icon in the user interfaceportion of the graphical program, and displaying a terminal in the blockdiagram portion of the graphical program corresponding to the icon. Insome embodiments, the user may specify or define a control or indicatorspecifically for the first data type, in which case the icon displayedin the user interface portion of the graphical program may be replacedwith the user-defined control or indicator. Examples of this type oficon are illustrated in FIG. 9, described below.

The method may also include executing the graphical program. Asindicated earlier, during execution of the graphical program, thegraphical user interface may be displayed on a display of a firstcomputer system and the block diagram may execute on a second computersystem.

FIGS. 6-9—Example Implementations of Wire Appearance Configuration Basedon Data Type

FIGS. 6-9 illustrate an example implementation of the methods describedabove with reference to FIGS. 5A and 5B. More specifically, FIGS. 6-8illustrate an example GUI for configuring a wire appearance to indicatedata type. Note that the embodiments shown are meant to be exemplaryonly, and are not intended to limit the invention to any particularform, function, or appearance.

FIG. 6 illustrates one embodiment of a GUI for specifying or configuringa wire appearance for a user-defined data type or class. As FIG. 6shows, in this embodiment, referred to as a “Class Wire Design Editor”,the GUI includes a dialog displaying various GUI elements for viewingand configuring wire appearance attributes, e.g., wire pattern andcolors. More specifically, in the embodiment shown, in the top left ofthe dialog a display of the current wire pattern may be seen. Belowthis, current colors used in the pattern are shown, as well as the pixelwidth(s) of the pattern, specifically, background color, foregroundcolor, and pixel width for a core and edges of the wire pattern.

In the center of the dialog, an example wire is shown in accordance withthe current configuration, and on the far right of the dialog, buttonsare provided for editing the core and edges.

FIG. 7 illustrates one embodiment of the GUI of FIG. 6 where a coloreditor dialog has been invoked to specify a color of an edge or core ofthe wire. For example, in one embodiment, the color editor dialog may beinvoked by clicking with a pointing device (e.g., a mouse) on one of theedit buttons (edge, core, edge) described above, and shown on the rightof the Class Wire Design Editor dialog. Alternatively, or in addition topressing the buttons, the user may invoke the color editor dialog byclicking on the displayed colors. In other embodiments, other means ofinvocation may be used, such as for example, selecting a menu item froma drop-down menu, and so forth.

As shown, the color editing dialog may receive user input specifying anyof a broad range of colors, which may then be applied to the portion ofthe wire appearance being edited (e.g., an edge or core) Once a color(e.g., for an edge or core) has been specified, the GUI may update thedisplay (e.g., the colors display and the example wire display) toreflect the specified color. This process may be repeated as desireduntil the colors for the wire are appropriately specified.

FIG. 8 illustrates one embodiment of the GUI of FIG. 6 where a patterneditor dialog has been invoked to specify a pattern for the wire. Invarious embodiments, the pattern editor dialog may be invoked in variousways, for example, via clicking on the wire pattern display field in thetop left side of the GUI dialog, by selecting a menu item from a dropdown menu, e.g., from the title bar, and so forth.

As FIG. 8 shows, in this embodiment, the pattern editor dialog maydisplay a plurality of pre-defined wire patterns from which the user mayselect a desired pattern. Once the desired pattern has been selected,the GUI may display the example wire in accordance with the specifiedpattern. Note that in the embodiment of FIG. 8, the GUI, including theexample wire display and color fields, is shown in grayscale, e.g., soas not to distract the user from the pattern information shown, althoughin other embodiments, the GUI may maintain the display of colors duringthe pattern specification process.

In another embodiment, the pattern editor dialog may provide a graphicalpixel-wise editor, whereby the user may define a new pattern by binaryactivation of pixels to specify an “atomic” unit of the pattern. Forexample, in one embodiment, a blank grid, e.g., an 8×8 pixel grid, maybe provided whereby the user may click on the grid at any location toturn a pixel at that location on or off. Once the user has defined theatomic element upon which the pattern is based, the GUI may replicatethe atomic element in sequential fashion to create a pattern, which maythen be displayed and/or saved for later use. In yet another embodiment,the user may use such a pixel-based edit facility to specify the patternand to specify the colors in the pattern.

It should be noted that presentation of a limited set of patterns in amenu for selection by the user is only one option contemplated, and thatmore general editors for creating arbitrary wire patterns are alsopossible and within the scope of this invention. For example, in variousembodiments, new wire appearance patterns may be imported from otherprograms or systems, or may be created and/or modified by users, e.g.,from “scratch” as desired.

FIG. 9 illustrates one embodiment of a graphical program, including ablock diagram, labeled “Untitled 1 Block Diagram”, and a front panel,labeled “Untitled 1 Front Panel”, where various user-defined classes areused, and where various wire appearances are displayed for the classes.Also shown is an example wire probe dialog for examining data on a wire,briefly described below. It should be noted that the examples shown inFIG. 9 are meant to be exemplary only, and are not intended to limit theinvention to any particular organization, functionality, or appearance.For example, while LabVIEW classes and objects may be referred to insome of the descriptions below, these are meant to be exemplary only,and are not intended to limit the classes, objects, data structures,and/or data types contemplated to any particular set or developmentsystem. Note also that elements shown in FIG. 9 that are not germane topresent invention are not described.

As FIG. 9 shows, the front panel includes various controls andindicators corresponding to usages of corresponding classes in the blockdiagram, including a control labeled “parent.rsc”, seen second from thetop in the front panel, and another control labeled “child.rsc”, justbelow the parent control. It should be noted that the names “parent” and“child” are meant to be illustrative only, indicating the inheritancerelationship between corresponding classes. The parent control isoperable to contain or store an instance of a user-defined class, inthis case, class “parent.rsc”, or any descendents of the parent class,and the child control is operable to contain or store an instance of auser-defined class “child.rsc”, which is derived from the parent class,as well as any descendents of the child class.

As shown in the block diagram, a terminal labeled “parent.rsc” andcorresponding to the parent control is connected to a thick graypatterned wire, presumably configured by the user for this parent class,and with an appearance specified for the “parent.rsc” class. This wireconnects the parent.rsc terminal to a build array node 902, which isconfigured to receive two inputs of the parent class (and/or adescendent class) and output an array of the same class. A similar wireconnects the build array node 902 to an appended array terminal, solabeled, which is associated with a corresponding appended arrayindicator on the front panel, also labeled “appended array”, whichoperates to store the array once it has been created by the build arraynode. As may also be seen, a terminal labeled “child.rsc” andcorresponding to the child control is connected to a thick dark wire,configured for this child class, and with an appearance specified forthe “child.rsc” class. This wire connects the child.rsc terminal to thebuild array node 902, and provides elements of the child.rsc class asinput to the build array node. The build array node 902 operates toreceive elements of both parent.rsc and child.rsc classes, and producesan array containing the elements.

Note that the wire connecting the build array node 902 to the appendedarray terminal has the same appearance as that from the parent.rscterminal; this is because the type of the created array is that of thenearest common ancestor class of the inputs in order to store elementsof different types/classes (i.e., parent.rsc and child.rsc classes),which in this case, is the parent.rsc class. Said another way, since theappended array includes data elements of the parent and child classes,the wire is of the parent class, and so has an appearance correspondingto that class.

Note also that the wire connecting the build array node 902 to theappended array terminal is slightly thicker than that connecting theparent terminal to the build array node 902, due to the increaseddimensionality of the data on the wire. In other words, the wireappearance corresponds to the dimensionality or number of elements ofthe data on the wire. Note further that the appended array indicator onthe front panel has an icon indicating the parent class.

Note that the wire connected to the child terminal also has a probe onit, denoted by the number “1”. This probe corresponds to the panellabeled “[1] child.rsc”, which, during execution of the graphicalprogram, displays the data on this wire. The probe shows the completedata for a child class which includes, as shown, all data from theparent class (a file path named ParentPath and a floating-point numericvalue named ParentSlide) and all data added by the child class (theremaining three data elements of ChildString, ChildError, andChildBool).

Thus, each of the data types, including user-defined data types and/orclasses, may have a corresponding wire appearance, and may also have acorresponding icon, for representation on the block diagram, and, in thecase of the icons, on the front panel as well. As shown in FIG. 9 anddescribed in detail above, data types or classes may inherit wireappearances from parent classes, and these wire appearances may beover-ridden. In other words, a class (child) may inherit its parent'swire appearance as a default, but this default wire appearance may bemodified or reconfigured by the user to provide a custom user-definedwire appearance for the child class. This child class, along with itsuser-defined wire appearance, may then be used to derive furtherdescendent classes as desired.

Thus, various embodiments of the techniques described above may enable auser to specify, configure, and re-configure, a wire appearance for awire associated with a user-defined data type or class in a graphicalprogramming environment.

Further Embodiments

The above embodiments are directed to defining and configuring wireappearance based on a user-defined data type or class; however, in otherembodiments, the user may define and configure wire appearance based onother attributes, e.g., based on specified functionality forcommunication between nodes in a graphical program.

FIGS. 10A and 10B—Method for Configuring a Wire Appearance IndicatingCommunication Functionality

FIGS. 10A and 10B flowchart methods for configuring a wire appearanceindicating communication functionality in a graphical programmingenvironment, according to one embodiment. The methods shown in FIGS. 10Aand 10B may be used in conjunction with any of the computer systems ordevices shown in the above Figures, among other devices. In variousembodiments, some of the method elements shown may be performedconcurrently, in a different order than shown, or may be omitted.Additional method elements may also be performed as desired. As shown,the method of FIG. 10A may operate as follows.

As shown in 1002, in one embodiment, first communication functionalitybetween nodes in a graphical program may be specified in response touser input. In various embodiments, specifying communicationfunctionality between nodes may include any of a plurality ofcommunication functionalities, including, for example, timing, or datatransfer, among others. Thus, for example, the user may provide inputspecifying communication of timing information between the nodes asopposed to data transfer (or, alternatively, data transfer between thenodes, as opposed to timing). A GUI may be used to specify thecommunication functionality.

Specifying timing may include, for example, specifying a clock, e.g., asource for a clock signal, specifying a timing signal, or specifyingwhether a leading or trailing edge of the clock or timing signal is tobe used, among others. In other words, specifying timing may includespecifying any attribute of timing functionality, as desired.

Specifying data transfer may include specifying data transfer semantics,a data transfer mechanism, and/or a data transfer medium. Data transfersemantics refers to the manner, e.g., policy, of data transfer, e.g.,synchronous, asynchronous, first-in, first-out (FIFO), buffered, etc.,and where data transfer mechanism refers to how the semantics areimplemented, e.g., via direct memory access (DMA), TCP/IP, sharedmemory, tags, and so forth. Thus, for one example, the user may specifythat data are to be communicated between two nodes asynchronously, andmay also specify that this asynchronous data transfer be implemented viaa particular data structure, e.g., a queue implemented via a linkedlist. More information regarding asynchronous (and synchronous) datatransfer may be found in U.S. patent application Ser. No. 11/462,393,titled “Asynchronous Wires for Graphical Programming”, which wasincorporated by reference above.

Thus, in some embodiments, specifying the first communicationfunctionality may include specifying data transfer semantics, which mayinclude specifying the method by which the data may be transferred,e.g., using a circular buffer, register, queues, and/or other bufferedsemantics, and/or may include specifying a data transfer mechanism,e.g., data transfer protocols, and/or other specifications related todata transfers. Specifying a data transport protocol may specify amethod for implementing the data transfer semantics for the wire. Forexample, the data transport protocol may be the specific protocol usedto transmit the data over the data transport medium (e.g., a networkedconnection, PCI bus, etc.). Exemplary data transport protocols includeTCP/IP, USB, DMA, register access, etc. Specifying a data transfermedium, which may also be referred to as a data transport medium, mayspecify the physical medium by which the data are transferred, e.g.,physical media such as wires, buses, Ethernet, etc., and/or wirelessmeans, among others.

Thus, for example, specifying the first communication functionality mayinclude specifying read or write policies for the wire, directionalityof the wire (e.g., the direction of data flow), semantics of wirebranching, and/or data structures associated with the wire, amongothers. As another example, in one embodiment, the wire may be specifiedto provide transport status information. For more information regardingspecifying data transport semantics and mechanisms, please see U.S.patent application Ser. No. 11/759,975, titled “Graphical Diagram WhichAutomatically Determines a Data Transport Mechanism For Wires Based OnConfigured Policies”, and U.S. patent application Ser. No. 11/759,991,titled “Diagram with Configurable Wires”, which were incorporated byreference above.

In 1004, a first wire appearance may be created in response to userinput, where the creating includes storing the first wire appearance.The first wire appearance is useable to be displayed for a wire in agraphical program that is configured to implement the specified firstcommunication functionality, and visually denotes or indicates thespecified first communication functionality of the wire.

Similar to that described above with respect to FIG. 5A above, inpreferred embodiments, creating the first wire appearance may includedisplaying a graphical user interface (GUI) for configuring the firstwire appearance, receiving user input to the GUI specifying a wirepattern, a wire thickness, a wire shape, one or more wire colors, atleast a portion of the wire to be configured with the first wireappearance, a wire label, and/or a wire icon to be displayed on orproximate to the wire, and creating the first wire appearance inaccordance with the user input to the GUI. One embodiment of a GUI forconfiguring the first wire appearance to denote or indicate the firstcommunication functionality is described below with reference to FIG.11. In various embodiments, the GUI for configuring the first wireappearance may be included in or invoked by a configuration tool, or maybe invoked by or under the graphical program development environment.

Note that other appearance attributes may be included as desired,including, for example, a shape, a 3D appearance, a tube appearance, aseparated appearance, a curved appearance, or an “extrusion shape”,e.g., “rectangular cross-section”, among others. In other words, anyvisual aspect of the wire may be used as desired to denote the specifiedcommunication functionality of the wire. For more information regardingwire appearances, please see U.S. patent application Ser. No.11/759,979, titled “Graphical Diagram Wires Whose Appearance RepresentsConfigured Semantics”, which was incorporated by reference above.

Note that in further embodiments, specifying the first communicationfunctionality may include specifying a model of computation to befollowed or implemented by the wire, such as, for example, Kahn ProcessNetworks (PN), or Communicating Sequential Processes (CSP), amongothers. In other words, in embodiments where a model of computationaffects or is affected by communication between nodes, the model ofcomputation for the wire may be specified, and a correspondingappearance used for the wire to denote the specified model ofcomputation.

As indicated in 1006, in some embodiments, a first graphical program maybe created, where the first graphical program includes a plurality ofinterconnected icons which visually indicate functionality of the firstgraphical program, including a first icon and a second icon. Creatingthe first graphical program may include connecting the first icon to thesecond icon in response to user input, and displaying a wire between thefirst icon and the second icon in response to the connecting, where thewire has the first wire appearance. Note that the graphical program maybe created in any of a variety of ways, as discussed above in methodelement 506 with reference to FIG. 5. In preferred embodiments, thefirst graphical program may be or include a graphical data flow program,although other types of graphical program are also contemplated, suchas, for example, control flow, execution flow, or state diagrams, amongothers. In one embodiment, the first graphical program may include ablock diagram portion comprising the plurality of interconnected icons,and a user interface portion, e.g., a front panel.

Note that in some embodiments, specifying communication functionalitybetween nodes may include specifying functionality of at least oneendpoint of the wire. For example, the behavior or mechanism of the“source” or “destination” end of the wire may be specified. Thus, forexample, a wire that is buffered may be specified to validate any datafrom the data source (node) before placing the data on the wire, i.e.,the behavior of the “source” end of the wire may be specified. Asanother example, the “destination” end of the wire may be specified tooutput default values if no data are currently on the wire. As anexample of specifying data transfer mechanisms, the “source” end of thewire may be specified to communicate with the source node via TCP/IP,while the “destination” end of the wire may be specified to communicatewith the destination node via register access.

Thus, in some embodiments, the first wire appearance may be or include aspecified appearance of a portion of the wire proximate to the at leastone endpoint of the wire. In other words, some aspects of the wire'sappearance may be specific to the end or ends, and may denotefunctionality thereof. Thus, depending upon the specified functionalityor functionalities of the wire, various portions of the wire may bedisplayed with respective appearances, e.g., patterns, colors,thicknesses, shapes, labels, icons (e.g., to be displayed on orproximate to the wire, decorations, etc., as desired, to denoterespective communication functionalities of the wire.

Thus, in some embodiments, creating the first wire appearance for thefirst communication functionality includes displaying a graphical userinterface (GUI) for configuring the first wire appearance, and receivinguser input to the GUI specifying one or more of: a wire pattern, one ormore wire colors, a wire thickness, a wire shape, at least a portion ofthe wire to be configured with the first appearance, a wire label,and/or a wire icon to be displayed on or proximate to the wire, andcreating the first wire appearance in accordance with the user input tothe GUI.

Thus, in some embodiments, the method may include displaying the firstwire appearance for a first wire in a first graphical program, where thefirst wire implements the specified first communication functionality,and where the first wire appearance visually specifies that the firstwire implements the specified first communication functionality.

As indicated in 1012 and 1014 of FIG. 10A, in some embodiments, themethod may optionally also include modifying the first wire appearancefor the first communication functionality in response to user input, anddisplaying the wire between the first icon and the second icon inresponse, where the wire has the modified first wire appearance. Thus,after the first communication functionality and wire appearance havebeen created and used in the graphical program, the user may be able toreconfigure or modify the wire appearance, in which case the wire in thegraphical program may be automatically updated in accordance with themodified wire appearance specified by the user. The wire appearance maybe modified via the same GUI used to create and specify the wireappearance initially, i.e., as described in 1004 above.

In some embodiments, the first wire appearance for the firstcommunication functionality may be inheritable. For example, the wireconfiguration corresponding to the specified first communicationfunctionality may be encapsulated in an inheritable data structure, andso may facilitate a modular approach to wire configuration, includingderiving additional wire configurations via inheritance. A derivedconfiguration, which may be referred to as a child configuration, mayinherit all of the functional specifications of the originalconfiguration, which may be referred to as a parent configuration, andmay optionally also include specification of additional communicationfunctionality. As with the data types/classes embodiments describedabove, in some embodiments, the wire appearance for a specifiedcommunication functionality may be inherited along with the specifiedcommunication functionality.

Thus, for example, as indicated in FIG. 10B, in one embodiment, themethod may include specifying a second communication functionalitybetween nodes in a graphical program in response to user input, wherethe second communication functionality is derived from the firstcommunication functionality, as indicated in 1022.

In 1024, a third icon and a fourth icon may be included in a graphicalprogram, where the third icon and the fourth icon are configured tocommunicate in accordance with the second communication functionality.For example, the third icon may be connected to the fourth icon inresponse to user input. Then, as indicated in 1026, a second wire may bedisplayed between the third icon and the fourth icon in response to theconnecting, e.g., automatically, where the second wire has the firstwire appearance. Thus, the first wire appearance may be used as a“default” wire appearance for communication functionalities derived fromthe first communication functionality.

Similar to above, in some embodiments, the method may further includemodifying the first wire appearance for the second communicationfunctionality in response to user input, and displaying the wire betweenthe third icon and the fourth icon in response to the modifying, wherethe wire has the modified first wire appearance, as indicated in 1028and 1030, respectively.

Alternatively, in some embodiments, a second wire appearance for thesecond communication functionality may be created in response to userinput, where, once the third icon is connected to the fourth icon inresponse to user input, a second wire may be displayed between the thirdicon and the fourth icon in response to the connecting, where the secondwire has the second wire appearance. In other words, the user may createa second wire appearance for the second communication functionality,e.g., overriding the “default” first wire appearance.

As above, the method may further include modifying the second wireappearance for the second communication functionality in response touser input, and displaying the wire between the third icon and thefourth icon in response to the modifying, where the wire has themodified second wire appearance.

As discussed above with reference to FIGS. 6-8, in preferredembodiments, a GUI may be provided whereby the user may create andmodify wire appearances. As noted above in the description of themethods of FIGS. 10A and 10B, in some embodiments, a wire appearance maybe created for a specified or created communication functionality, andmay then be associated with that functionality such that when graphicalprogram nodes are configured to communicate according to the specifiedcommunication functionality, the associated wire appearance mayautomatically be used to display a wire connecting the nodes. In otherwords, if the nodes are configured according to the specifiedcommunication functionality, a wire connecting the nodes mayautomatically have the wire appearance (whether the connection isperformed manually or automatically).

In one embodiment, the GUI may provide means whereby the user mayspecify the association between the created wire appearance and thespecified communication functionality. For example, the GUI may allowthe user to search or browse a directory to locate a particularcommunication functionality, e.g., in the form of a file or datastructure, and to select the communication functionality for associationwith the created wire appearance. Additionally, in further embodiments,the GUI may facilitate creation and/or management of inheritancerelationships among communication functionalities and/or wireappearances, discussed above.

Of course, in other embodiments, other means may be used to selectand/or associate the wire appearance with a communication functionality,as desired.

FIG. 11—Exemplary Graphical Program Utilizing Various CommunicationFunctionalities with Corresponding Wires

FIG. 11 illustrates one embodiment of a graphical program where varioususer-defined communication functionalities are used, and wherecorresponding wire appearances are displayed for the respectivecommunication functionalities.

As FIG. 11 shows, in this exemplary embodiment, the communicationfunctionality of a first wire 1102 has been configured for timing, andthe communication functionality of a second wire 1104 has beenconfigured for data transfer. Note that each wire has a distinctiveappearance indicating its communication functionality. For example, thetiming wire 1102 has a 3D shaded tubular appearance (and may also have aspecified color), whereas the data transfer wire 1104 has not only adifferent wire pattern (and possibly a different color), but alsoincludes an icon indicating the particular data transfer functionalityspecified for the wire. It should be noted that the examples shown inFIG. 11 are meant to be exemplary only, and are not intended to limitthe invention to any particular organization, functionality, orappearance. For further examples of communication functionalities andexemplary associated wire appearances and icons, please see U.S. patentapplication Ser. No. 11/759,979, titled “Graphical Diagram Wires WhoseAppearance Represents Configured Semantics”, filed Jun. 8, 2007, whichwas incorporated by reference above.

Thus, various embodiments of the above systems and methods may allow auser to define or specify communication functionality between two nodesin a graphical program, as well as a first wire appearance indicating,representing, or denoting the specified functionality. The first wireappearance may then be used in a graphical program to visually indicatewires with that functionality.

Although the embodiments above have been described in considerabledetail, numerous variations and modifications will become apparent tothose skilled in the art once the above disclosure is fully appreciated.It is intended that the following claims be interpreted to embrace allsuch variations and modifications.

1. A computer-accessible memory medium comprising program instructions,wherein the program instructions are executable by a processor toimplement: specifying a first communication functionality between nodesin a graphical program in response to user input defining a newcommunication functionality; creating a first wire appearance forrepresenting the first communication functionality in response to userinput defining the first wire appearance, wherein said creatingcomprises storing the first wire appearance to be subsequently used fora wire that is configured to implement the first communicationfunctionality, wherein the first communication functionality comprisesone or more of: timing; or data transfer, comprising one or more of:data transfer semantics, a data transfer mechanism, or a data transfermedium, and subsequently displaying a first wire in a first graphicalprogram, wherein the first wire is configured to implement the specifiedcommunication functionality, wherein the first wire is displayed withthe first wire appearance, and wherein the first wire appearancevisually denotes the specified communication functionality of the wire.2. The memory medium of claim 1, wherein the program instructions arefurther executable to implement: creating the first graphical program,wherein the first graphical program comprises a plurality ofinterconnected icons which visually indicate functionality of the firstgraphical program, including a first icon and a second icon, and whereinsaid creating the first graphical program comprises: connecting thefirst icon to the second icon in response to user input; and whereinsaid displaying the first wire comprises displaying the first wirebetween the first icon and second icon in response to said connecting.3. The memory medium of claim 2, wherein the program instructions arefurther executable to implement: modifying the first wire appearance inresponse to user input, wherein said modifying produces a modified firstwire appearance; and displaying the first wire between the first iconand the second icon with the modified first wire appearance in responseto said modifying.
 4. The memory medium of claim 2, wherein the firstwire appearance is inheritable, and wherein the program instructions arefurther executable to implement: specifying a second communicationfunctionality between nodes in a graphical program in response to userinput, wherein the second communication functionality is derived fromthe first communication functionality; including a third icon and afourth icon in a second graphical program, wherein the third icon andthe fourth icon are configured to communicate in accordance with thesecond communication functionality, wherein said including comprises:connecting the third icon to the fourth icon in response to user input;and displaying a second wire between the third icon and the fourth iconin response to said connecting, wherein the second wire has the firstwire appearance.
 5. The memory medium of claim 4, wherein the programinstructions are further executable to implement: modifying the firstwire appearance for the second communication functionality in responseto user input; and displaying the second wire between the third icon andthe fourth icon in response to said modifying, wherein the wire has themodified first wire appearance.
 6. The memory medium of claim 2, whereinthe first wire appearance is inheritable, and wherein the programinstructions are further executable to implement: specifying a secondcommunication functionality between nodes in a graphical program inresponse to user input, wherein the second communication functionalityis derived from the first communication functionality; creating a secondwire appearance for the second communication functionality in responseto user input; including a third icon and a fourth icon in a secondgraphical program, wherein the third icon and the fourth icon areconfigured to communicate in accordance with the second communicationfunctionality, wherein said including comprises: connecting the thirdicon to the fourth icon in response to user input; and displaying asecond wire between the third icon and the fourth icon in response tosaid connecting, wherein the second wire has the second wire appearance.7. The memory medium of claim 2, wherein the first graphical programcomprises a block diagram portion comprising the plurality ofinterconnected icons, and a user interface portion.
 8. The memory mediumof claim 2, wherein the first graphical program comprises a graphicaldata flow program.
 9. The memory medium of claim 1, wherein saidcreating the first wire appearance comprises: displaying a graphicaluser interface on the display; and receiving user input to the graphicaluser interface specifying the first wire appearance for the firstcommunication functionality.
 10. The memory medium of claim 9, whereinsaid specifying the first wire appearance for the first communicationfunctionality comprises specifying one or more of: a wire pattern; awire thickness; a wire shape; one or more wire colors; or at least aportion of the wire to be configured with the first wire appearance. 11.The memory medium of claim 9, wherein said specifying the first wireappearance for the first communication functionality comprisesspecifying one or more of: a wire label; or a wire icon to be displayedon or proximate to the wire.
 12. The memory medium of claim 1, whereinsaid specifying the first communication functionality between nodescomprises specifying a model of computation to be followed orimplemented by the wire.
 13. The memory medium of claim 1, wherein saidspecifying the first communication functionality between nodes comprisesspecifying functionality of at least one endpoint of the wire; andwherein the first wire appearance includes a specified appearance of aportion of the wire proximate to the at least one endpoint of the wire.14. The memory medium of claim 1, wherein the first wire appearance isinheritable.
 15. A method for configuring a wire appearance in agraphical program, the method comprising: utilizing a computer toperform: specifying a first communication functionality between nodes ina graphical program in response to user input defining a newcommunication functionality; creating a first wire appearance forrepresenting the first communication functionality in response to userinput defining the first wire appearance, wherein said creatingcomprises storing the first wire appearance to be subsequently used fora wire that is configured to implement the first communicationfunctionality, wherein the first communication functionality comprisesone or more of: timing; or data transfer, comprising one or more of:data transfer semantics, a data transfer mechanism, or a data transfermedium, and subsequently displaying a first wire in a first graphicalprogram, wherein the first wire has the first wire appearance, whereinthe first wire is configured to implement the specified communicationfunctionality, and wherein the first wire appearance visually denotesthe specified communication functionality of the wire.
 16. The method ofclaim 15, further comprising: creating the first graphical program,wherein the first graphical program comprises a plurality ofinterconnected icons which visually indicate functionality of the firstgraphical program, including a first icon and a second icon, and whereinsaid creating the first graphical program comprises: connecting thefirst icon to the second icon in response to user input; and whereinsaid displaying the first wire comprises displaying the first wirebetween the first icon and second icon in response to said connecting.17. The method of claim 16, wherein the first wire appearance isinheritable, the method further comprising: specifying a secondcommunication functionality between nodes in a graphical program inresponse to user input, wherein the second communication functionalityis derived from the first communication functionality; including a thirdicon and a fourth icon in a second graphical program, wherein the thirdicon and the fourth icon are configured to communicate in accordancewith the second communication functionality, wherein said includingcomprises: connecting the third icon to the fourth icon in response touser input; and displaying a second wire between the third icon and thefourth icon in response to said connecting, wherein the second wire hasthe first wire appearance.
 18. The method of claim 16, wherein the firstwire appearance is inheritable, the method further comprising:specifying a second communication functionality between nodes in agraphical program in response to user input, wherein the secondcommunication functionality is derived from the first communicationfunctionality; creating a second wire appearance for the secondcommunication functionality in response to user input; including a thirdicon and a fourth icon in a second graphical program, wherein the thirdicon and the fourth icon are configured to communicate in accordancewith the second communication functionality, wherein said includingcomprises: connecting the third icon to the fourth icon in response touser input; and displaying a second wire between the third icon and thefourth icon in response to said connecting, wherein the second wire hasthe second wire appearance.
 19. A system for configuring a wireappearance in a graphical program, the system comprising: a processor;and a memory medium coupled to the processor, wherein the memory mediumstores program instructions which are executable by the processor to:specify a first communication functionality between nodes in a graphicalprogram in response to user input defining a new communicationfunctionality; create a first wire appearance for representing the firstcommunication functionality in response to user input defining the firstwire appearance, wherein said creating comprises storing the first wireappearance to be subsequently used for a wire that is configured toimplement the first communication functionality, wherein the firstcommunication functionality comprises one or more of: timing; or datatransfer, comprising one or more of: data transfer semantics, a datatransfer mechanism, or a data transfer medium, and subsequently displaya first wire in a first graphical program, wherein the first wire hasthe first wire appearance, wherein the first wire is configured toimplement the specified communication functionality, and wherein thefirst wire appearance visually denotes the specified communicationfunctionality of the wire.
 20. The system of claim 19, wherein theprogram instructions are further executable to: create the firstgraphical program, wherein the first graphical program comprises aplurality of interconnected icons which visually indicate functionalityof the first graphical program, including a first icon and a secondicon, and wherein said creating the first graphical program comprises:connecting the first icon to the second icon in response to user input;and wherein said displaying the first wire comprises displaying thefirst wire between the first icon and second icon in response to saidconnecting.
 21. A system for configuring a wire appearance in agraphical program, the system comprising: means for specifying a firstcommunication functionality between nodes in a graphical program inresponse to user input defining a new communication functionality; meansfor creating a first wire appearance for representing the firstcommunication functionality in response to user input defining the firstwire appearance, wherein said creating comprises storing the first wireappearance to be subsequently used for a wire that is configured toimplement the first communication functionality, wherein the firstcommunication functionality comprises one or more of: timing; or datatransfer, comprising one or more of: data transfer semantics, a datatransfer mechanism, or a data transfer medium, and means forsubsequently displaying a first wire in a first graphical program,wherein the first wire has the first wire appearance, wherein the firstwire is configured to implement the specified communicationfunctionality, and wherein the first wire appearance visually denotesthe specified communication functionality of the wire.